Reviewer's Guide

Adjusts the blog detail frontend action to use the first URL segment for the post identifier and registers a dedicated Blog Detail frontend block extra in the backend installer so blog detail pages can be configured as separate pages.

Sequence diagram for blog detail request resolving first URL segment

sequenceDiagram
  actor User
  participant FrontendRouter
  participant BlogDetailAction
  participant Url
  participant FrontendBlogModel

  User->>FrontendRouter: GET /my-post-slug
  FrontendRouter->>BlogDetailAction: dispatch detail action
  BlogDetailAction->>Url: getParameter 0
  Url-->>BlogDetailAction: postIdOrSlug
  BlogDetailAction->>Url: getParameter revision,int
  Url-->>BlogDetailAction: revisionOrNull
  alt revision is null
    BlogDetailAction->>FrontendBlogModel: get postIdOrSlug
    FrontendBlogModel-->>BlogDetailAction: post
  else revision is set
    BlogDetailAction->>FrontendBlogModel: getRevision postIdOrSlug,revision
    FrontendBlogModel-->>BlogDetailAction: postRevision
  end
  BlogDetailAction-->>FrontendRouter: render blog detail page
  FrontendRouter-->>User: HTML response

Flow diagram for registering the Blog Detail frontend block extra

flowchart LR
  subgraph BackendInstaller
    Installer[Blog Installer]
  end

  Installer -->|configureFrontendExtras| InsertExtraBlog[insertExtra Blog block]
  Installer -->|configureFrontendExtras| InsertExtraDetail[insertExtra Detail block]
  Installer -->|configureFrontendExtras| InsertExtraArchive[insertExtra Archive widget]
  Installer -->|configureFrontendExtras| InsertExtraCategories[insertExtra Categories widget]
  Installer -->|configureFrontendExtras| InsertExtraRecentArticlesFull[insertExtra RecentArticlesFull widget]

  InsertExtraBlog --> ModuleExtras[Module extra records]
  InsertExtraDetail --> ModuleExtras
  InsertExtraArchive --> ModuleExtras
  InsertExtraCategories --> ModuleExtras
  InsertExtraRecentArticlesFull --> ModuleExtras

  subgraph Frontend
    BlogOverviewPage[Page with Blog block]
    BlogDetailPage[Page with Detail block]
  end

  ModuleExtras --> BlogOverviewPage
  ModuleExtras --> BlogDetailPage

File-Level Changes

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.